\section{Introduction} 
\subsection{Project purpose}
Project consists in urbanisation of Information System. To have a
first view of IS we'll build a \SM{} in \tsf{MS Visio}. But this kind
of map is not reactive, not easy to communicate it to other services,
not very comfortable for reporting and limited in information which we
can put on for each application or infrastructure element. So aim of
this document is to describe tool which will provide us more
flexibility in this kind of work.

\subsection{Project actors}
Guillaume \tsc{Doriry}, \MIS{} Account Manager and Application Manager
for France and South Europe initiated this project. Working group
members are Tea \tsc{Chkhaberidze}, BIS team, Jean-Christophe
\tsc{Pierson} and Giorgi \tsc{Beridze} from \tsf{LAS team}. This work
will be done with the co-operation of all members of \tsf{BIS},
\tsf{LAS} and other teams of \MIS{}. Also Account managers' community
and deferent services of Business.

\subsection{References}
\begin{itemize}
\item We don't have any documentation describing potential tool.
\item There is no any standard imposed for this tool.
\item Design document of \SM{}.
\end{itemize}

\section{Context}
\subsection{Goals}
We need to know about all applications used on HAG site, also related
infrastructure elements. For each software and infrastructure
equipment we defined what is the information we'd like to appear on
\SM{}. For further information you could refer
to~\ref{an:sm_specifications}.

It's impossible to manage all these data with \tsf{MS Visio}, also we
have problems to maintain \SM{} updated. The information must be
centralised.  One of important feature of this software is the
database where we'll be able to stock all data we've got. This tool
must allow us to communicate easier with other teams, good and
intuitive reporting possibility. Filter and visualise the application
with different criterions.

\section{General Description}
\subsection{Integration in our system}
This product can be an independent one with own database, which will
not interact with other applications. And which provide a reporting
system of her own. But for this moment we are working on the
possibility to build the system which will be able to inquire directly
\tsf{CMDB} (ITIL). We need to make some changes on existing data model, to
put in all information we've got up about applications. This is Oracle
database managed by \tsf{ESP team}. Nowadays only one software called
\MAGIC{} access this base. \MAGIC{} is used for incident, change
management\dots So in the database we have already some information
about application and infrastructure equipment. We'll need to complete
the database and create interface with future application for system
map management.

\subsection{Tool's functions}
Functions that are expected from the tool are:
\begin{itemize}
\item Read/Write in database
\item Generate automatically system map from database
\item Data import/export functionality
\item User management
\item Generate diagrams of applications with some specified
criterions. (desktop, obsolete)
\item Reporting system
\end{itemize}

\subsection{Constraints}
The tool must not be expensive. \\ 

Dependencies on other software like newest version of \textsf{MS
Visio} or specific database.\\

Constraints of exploitation: tool can be rejected by users because of
its complexity;

\section{Detailled description}
\subsection{Functionnal specification}
The figure~\ref{fig:functionnal_spec_tool} presents the functionnal
specifications. 
\begin{figure}[!htbp]
	\centering
%	\includegraphics[width=\lfig]{graph/functionnal_spec_tool}
	\caption{Functionnal specifications}
	\label{fig:functionnal_spec_tool}
\end{figure}

\subsection{Main criterions}
\begin{itemize}
\item Have a different user modes, with different permissions
\item Create the objects (application/Infrastructure element)(name,
version\dots) 
\item Create the interfaces between two or more objects (links)
\item Specify type of link
\item Save objects in database
\item Change and delete objects
\item Make the relation between the application and Infrastructure
element
\item Generate drawing from DB
\item Make changes on drawing and save it
\item Search object in DB and visualise all about it
\item Export data in different formats (XML, Excel,\dots)
\item Import data from another software (XML, Excel, \dots)
\item Zooming, drill down functionality. 
\item Versioning off maps, applications\dots
\item Support, maintenance supplier
\item Possibility to highlight critical objects (ex: no future soft)
\item Price
\end{itemize}

We need to know about system requirements, hard (CPU, disk space
needed), other soft (\tsf{MS Visio}) and data base type (SQL, Oracle\dots)

\subsection{Interfaces' specification}
\begin{description}
\item[soft to soft] Potentially with Oracle database (CMDB). 
\item[soft to man] Interfaces for database manipulation, for drawing
visualisation and modification.
\end{description}

\subsection{Quality requirements}
Quality requirements we were looking at are:
\begin{itemize}
\item Response time
\item Images quality
\item Efficiency
\item Operational safety
\end{itemize}
